I get this when trying to connect to my local machine's instance of Reporting Services. I know that it's running because I can push reports and run reports. I've even managed to edit the config file so I can send e-mails through a data-driven subscription. However, I cannot connect to my Reporting Services instance through the 2008 Configuration Manager. I always get an "invalid namespace" message.Any suggestions?

Hi Paschott, Which Version of SQL Server that you are using in your machine

I am hitting the same issue. Server 2008 Standard RTM, SQL Server 2008 Enterprise RTM.

I am getting exactly the same error. Anyone have any ideas of what might be occuring?

Hi Powell, You are also getting the same issue? When you are getting this issue. Can you provide more info about the scenario when this is fired.

Hi, The post appears to be related to Reporting Services 2008. This forum is provided for Reporting Services 2000 and 2005. You may find support for it at http://forums.microsoft.com/TechNet/ShowForum.aspx?ForumID=1624&SiteID=17If there are anymore questions, please let me know. Thanks.

The sticky post at the top of that forum (http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3736796&SiteID=17) says to direct all questions to this forum. I'm also getting this error, a long with acouple of other guys here. We are all using the developer edition on Vista. If you get the installer to do the reporting services default setup it seems to work ok (database is created and the reports and reportserver URL work ok) you just can't connect the reporting services configuration tool to check the configuration. One guy didn't choose to do the default reporting services install and now has to un-install the lot to get it to work (the option to do the default install is greyed out if you have already done the install previously). Some weird things I have seen The old 2005 reporting services configuration tool (I have 2005 and 2008 installed side by side, 2005 is the default instance) can connect quite happily to the 2008 reporting services instance, but obviously is pretty stuffed from there. When you open the SQL Server Configuration Manager, select the reporting services service / properties and click the configure button it opens the 2005 tool instead of the 2008 one. Can connect to the instance using Management studio Can connect to the report server and report manager I've tried using the run as administrator option as well with no luck (have got the UAC turned off anyway).

Hi Im replying just to confirm posts above. My setup:OS Windows Vista Business x86 SP1 UAC off from start.SQL Server 2005 Developer SP2 Default Instance all servicesSQL Server 2008 Developer Named Instance all services Im experiencing same problems as stated above.When I start Reporting Service Configuration for 2008 it doesnt connect to reporting service.If I start Reporting Service Configuration for 2005 I can connect to 2008 instance but cannot configure it.

Hi, Modify the Connection Strings in rsreportserver.config, it should redirect to the SQL Server 2005 Instance. Can you check event vwr and let me know what is the error when you try to connect to reporting service

No errors in the event log or the RS log file. Which connection string in the rsreportserver.config file ar eyou refering to?

SSRS 2005 WMI namespace is changed in SSRS 2008 release and the namespace is not backwards compatible. Also inSSRS 2008 release cycle, the namespace has gone through changes between CTP6 and RC0 versions. So if you are using Reporting Services Configuration tool from prior RC0 versions to configure RTM instance, you can run into "Invalid Namespace" error. What namespace is yourreportingServices.mof file pointing to. You can see the mof file in <installlocation>\reportingservices\reportserver\bin Also it is a known issue that 2008 SQL Server Configuration manager points to 2005 version of Reporting Services Configuration tool. We are coming up with a KB article for it.

I didn't have any of the ctp's or rc0 on this machine so it is a clean RTM install. the mof file is #pragma autorecover#pragma namespace ("\\\\.\\Root") instance of __Namespace { Name = "Microsoft";}; #pragma namespace ("\\\\.\\Root\\Microsoft")instance of __Namespace { Name = "SqlServer";}; #pragma namespace ("\\\\.\\root\\Microsoft\\SqlServer")instance of __Namespace { Name = "ReportServer";}; #pragma namespace ("\\\\.\\root\\Microsoft\\SqlServer\\ReportServer") instance of __Namespace { Name = "RS_SQL2008";}; #pragma namespace ("\\\\.\\root\\Microsoft\\SqlServer\\ReportServer\\RS_SQL2008") instance of __Namespace { Name = "v10";}; #pragma namespace ("\\\\.\\root\\Microsoft\\SqlServer\\ReportServer\\RS_SQL2008\\V10") //*************************************************************//*** Namespace: v10 ***//*************************************************************instance of __Win32Provider as $P{ Name = "ReportingServicesWMI"; ClsId = "{718032C8-EDE1-4C52-9745-6D9A7B478413}";HostingModel = "LocalSystemHostOrSelfHost";}; instance of __InstanceProviderRegistration{ Provider = $P; SupportsGet = TRUE; SupportsPut = FALSE; SupportsDelete = FALSE; SupportsEnumeration = TRUE; QuerySupportLevels = {"WQL:UnarySelect"};}; instance of __MethodProviderRegistration{ Provider = $P;}; //**************************************************************************//* Class: MSReportServer_Instance (lives in v10)//**************************************************************************[dynamic: ToInstance, provider("ReportingServicesWMI")]class MSReportServer_Instance{ [read] string InstanceID; [key, read] string InstanceName; [read] uint32 EditionID; [read] string EditionName; [read] boolean IsSharePointIntegrated; [read] string Version; [implemented] void GetReportServerUrls( [out] string ApplicationName[], [out] string URLs[], [out] sint32 Length, [out] sint32 HRESULT);}; instance of __Namespace { Name = "Admin";}; #pragma namespace ("\\\\.\\root\\Microsoft\\SqlServer\\ReportServer\\RS_SQL2008\\V10\\admin") //*************************************************************//*** Namespace: Admin ***//*************************************************************instance of __Win32Provider as $Q{ Name = "ReportingServicesWMI"; ClsId = "{718032C8-EDE1-4C52-9745-6D9A7B478413}";HostingModel = "LocalSystemHostOrSelfHost";}; instance of __InstanceProviderRegistration{ Provider = $Q; SupportsGet = TRUE; SupportsPut = TRUE; SupportsDelete = FALSE; SupportsEnumeration = TRUE; QuerySupportLevels = {"WQL:UnarySelect"};}; instance of __MethodProviderRegistration{ Provider = $Q;}; //**************************************************************************//* Class: MSReportServer_ConfigurationSetting (lives in Admin)//**************************************************************************[dynamic: ToInstance, provider("ReportingServicesWMI")]class MSReportServer_ConfigurationSetting{ [read] sint32 ConnectionPoolSize; [read] string DatabaseLogonAccount; [read] sint32 DatabaseLogonTimeout; [read] sint32 DatabaseLogonType; [read] string DatabaseName; [read] sint32 DatabaseQueryTimeout; [read] string DatabaseServerName; [key, read] string InstanceName; [read] string InstallationID; [read] boolean IsInitialized; [read] boolean IsWindowsServiceEnabled; [read] boolean IsWebServiceEnabled; [read] boolean IsReportManagerEnabled; [read] string MachineAccountIdentity; [read] string PathName; [read] sint32 SecureConnectionLevel; [read] string SenderEmailAddress; [read] string ServiceName; [read] boolean SendUsingSMTPServer; [read] string SMTPServer; [read] string UnattendedExecutionAccount; [read] string WindowsServiceIdentityActual; [read] string WindowsServiceIdentityConfigured; [read] boolean IsSharePointIntegrated; [read] string Version; [read] string VirtualDirectoryReportServer; [read] string VirtualDirectoryReportManager; [implemented] void InitializeReportServer( [in] string InstallationID, [out] sint32 HRESULT, [out] string ExtendedErrors[]); [implemented] void SetUnattendedExecutionAccount( [in] string UserName, [in] string Password, [out] sint32 HRESULT); [implemented] void RemoveUnattendedExecutionAccount( [out] sint32 HRESULT); [implemented] sint32 SetDatabaseConnection( [in] string Server, [in] string DatabaseName, [in] sint32 CredentialsType, [in] string UserName, [in] string Password, [out] sint32 HRESULT); [implemented] void SetEmailConfiguration( [in] boolean SendUsingSmtpServer, [in] string SmtpServer, [in] string SenderEmailAddress, [out] sint32 HRESULT); [implemented] sint32 SetWindowsServiceIdentity( [in] boolean UseBuiltInAccount, [in] string Account, [in] string Password, [out] sint32 HRESULT); [implemented] void GenerateDatabaseCreationScript( [in] string DatabaseName, [in] sint32 Lcid, [in] boolean IsSharePointMode, [out] string Script, [out] sint32 HRESULT); [implemented] void GenerateDatabaseRightsScript( [in] string UserName, [in]string DatabaseName, [in]boolean IsRemote, [in] boolean IsWindowsUser, [out] string Script, [out] sint32 HRESULT); [implemented] void GenerateDatabaseUpgradeScript( [in] string DatabaseName, [in] string ServerVersion, [out] string Script, [out] sint32 HRESULT); [implemented] void BackupEncryptionKey( [in] string Password, [out] uint8 KeyFile[], [out] sint32 Length, [out] sint32 HRESULT, [out] string ExtendedErrors[]); [implemented] void RestoreEncryptionKey( [in] uint8 KeyFile[], [in] sint32 Length, [in] string Password, [out] sint32 HRESULT, [out] string ExtendedErrors[]); [implemented] void SetSecureConnectionLevel( [in] sint32 Level, [out] sint32 HRESULT); [implemented] void DeleteEncryptedInformation( [out] sint32 HRESULT, [out] string ExtendedErrors[]); [implemented] void DeleteEncryptionKey( [in] string InstallationID, [out] sint32 HRESULT, [out] string ExtendedErrors[]); [implemented] void ListReportServersInDatabase( [out] string MachineNames[], [out] string InstanceNames[], [out] string InstallationIDs[], [out] boolean IsInitialized[], [out] sint32 Length, [out] sint32 HRESULT, [out] string ExtendedErrors[]); [implemented] void ReencryptSecureInformation( [out] sint32 HRESULT, [out] string ExtendedErrors[]); [implemented] void SetDatabaseLogonTimeout( [in] sint32 LogonTimeout, [out] sint32 HRESULT); [implemented] void SetDatabaseQueryTimeout( [in] sint32 QueryTimeout, [out] sint32 HRESULT); [implemented] void SetServiceState( [in] boolean EnableWindowsService, [in] boolean EnableWebService, [in] boolean EnableReportManager, [out] sint32 HRESULT); [implemented] void ListInstalledSharePointVersions( [out] string VersionTokens[], [out] sint32 Length, [out] sint32 HRESULT); [implemented] void GetDatabaseVersionDisplayName( [in] string Version, [out] string DisplayName, [out] sint32 HRESULT); [implemented] void GetAdminSiteUrl( [out] string AdminSiteUrl, [out] sint32 HRESULT); [implemented] void ListReservedUrls( [out] string Application[], [out] string UrlString[], [out] string Account[], [out] string AccountSID[], [out] sint32 Length, [out] sint32 HRESULT); [implemented] void SetVirtualDirectory( [in] string Application, [in] string VirtualDirectory, [in] sint32 Lcid, [out] string Error, [out] sint32 HRESULT); [implemented] void ReserveURL( [in] string Application, [in] string UrlString, [in] sint32 Lcid, [out] string Error, [out] sint32 HRESULT); [implemented] void RemoveURL( [in] string Application, [in] string UrlString, [in] sint32 Lcid, [out] string Error, [out] sint32 HRESULT); [implemented] void ListSSLCertificates( [out] string CertificateHash[], [out] string CertName[], [out] string Hostname[], [out] sint32 Length, [out] sint32 HRESULT); [implemented] void ListIPAddresses( [out] string IPAddress[], [out] string IPVersion[], [out] boolean IsDhcpEnabled[], [out] sint32 Length, [out] sint32 HRESULT); [implemented] void ListSSLCertificateBindings( [in] sint32 Lcid, [out] string Application[], [out] string CertificateHash[], [out] string IPAddress[], [out] sint32 Port[], [out] string Errors[], [out] sint32 Length, [out] sint32 HRESULT); [implemented] void CreateSSLCertificateBinding( [in] string Application, [in] string CertificateHash, [in] string IPAddress, [in] sint32 Port, [in] sint32 Lcid, [out] string Error, [out] sint32 HRESULT); [implemented] void RemoveSSLCertificateBindings( [in] string Application, [in] string CertificateHash, [in] string IPAddress, [in] sint32 Port, [in] sint32 Lcid, [out] string Error, [out] sint32 HRESULT);};

This may be related to a known issue in the Config Tool when SQL 2005 and SQL 2008 are installed on the same machine. Depending on the SQL 2008 instance name, this issue may or may not appear. Would it be possible to try uninstalling the SQL 2008 instance and reinstalling it using a different instance name, such as SQL8 or NAMEDINSTANCE?

Steps to modify the MOF file to fix this issue: 1. Locate the existing MOF file (example: %ProgamFiles%\Microsoft SQL Server\MSRS10.SQL2008\Reporting Services\ReportServer\bin\reportingservices.mof would be the default location for a Reporting Services instance named SQL2008). 2. Copy this reportingservices.mof to reportingservicesalt.mof (or some other unique name). 3. Notepad reportingservicealt.mof 4. Choose edit->replace 5. In the dialog, in the Find What: text box enter the modified instance name (for an RS instance named SQL2008, the modified instance name is RS_SQL2008), in the Replace with: text box enter the instance name unmodified (so for an RS instance named SQL2008, just enter SQL2008). 6. Press the Replace All button. 7. Save and close notepad. 8. From a command window at the same location as the results of step 1, type MOFCOMP REPORTINSERVICESALT.MOF (or whatever the name from step 2 was). Now the configuration tool should work with the following exception, if the RS instance name contains an underscore (_), a dollar sign ($) or a hash (#), then step 8 will fail and the user will need to re-install the Reporting Services instance with a name that does not include any of these three characters.

Thanks Dave. That solved my problem and this thread helped explain a few things for me. Now a happy camper .Thanks all.

Note that this is a known issue that occurs when SQL 2005 and SQL 2008 RS exists on the same machine. This issue may or may not appear based on the instance name you have for SQL 2008 RS. We will be coming up with a KB article for this issue soon.

Thanks Dave you save me....after 3 days of debuging my FormAuthentitacion for 2008 SQL Reporting Service works OK

Thanks, Dave. This worked for me. I have no idea why I didn't get the original requests for more information. I guess I need to check my hotmail account to see if I got anything there besides Spam. Of course, this doesn't seem to address my impersonation issue writing DDS's to a file server, but that's a whole 'nother story/problem. I appreciate the help.

I am using SSRS 2005, On the drill down of the report the error occurs: THis error does not occur with IE 7 or Firefox, only IE 6. Drilling down the first time is not a problem but when hitting the back button and clicking drill down link again the following error occurs: The path of the item '(null)' is not valid. The full path must be less than 260 characters long; other restrictions apply. If the report server is in native mode, the path must start with slash. (rsInvalidItemPath) I read from some blogs that it is known issue. or it is resolve ? Any Idea? Thanks

I am having this problem using Management Studio for 2008 on my laptop connecting to SQL2005 instances of Reporting Services, but no database server installed, so I don't have a .MOF file to edit. I do have Managemenst Studio for SQL2005 installed on the same machine. Any news on the KB article number please? MSDN is down so I can't find it today.

I think you will need to use SSMS 2005 to work with SSRS 2005. A lot of the functionality that was in SSMS in 2005 was moved into Report Manager in 2008 and there is not too much left in SSMS in 2008 for SSRS.

Adey11, The WMI namespace is changed between SQL 2005 and SQL 2008 releases. That is the reason you are having this problem while connecting to 2005 instance from SSMS 2008. Try specifying the 'ServerName" in the "Connect To Server" dialog of SSMS as your 2005 report server URL (for ex: http://<servername>/reportserver). This will resolve your problem. ------- Also I want to add some clarity on the changes done to SSMS reporting services functionality in 2008. Starting from SQL 2008 release, SSMS is intended to be used as admin only tool tomanage reporting services. Hence the ability to view/manage reports is removed from SSMS. Report Manager is the tool for end users to view/interact/manage reports. Some of the functionality we had in 2005 report manager (such as jobs, system properties etc) is moved to SSMS as well in 2008 time frame.

Thanks Neeraja for this solution. I am now able to connect using the URL from MS 2008 to SSRS 2005. Thanks too for the warning about the changes. More learning ahead...

When you say step 8 will fail, what will the error be? I have followed the steps with no : _ $ # and I'm still getting an error: Storing data in the repository...An error occurred while processing item x defined on lines x-x in file reportingservicesalt.mof:Error Number:0x80041003, Facility: WMIDescription: Access deniedCompiler returned error 0x80041003 I'm wondering if this is the error you are talking about or is this a separate issue? Thanks.

This is a separate issue. Are you on Vista or Windows Server 2008? If so, did you launch your command window as an administrator?

I got it to work....Thanks Dave. Vista is a pain!

I am experiencing the same issue. Getting the "ReportServer Url. Invalid namespace" when logging into Report Manager through the URL. I am using SQL 2008 with Forms Authentication. I have followed the changes in the MOF file, but am not having any luck. The only difference I can see here is that I do not have a named instance of SQL Server 2008. So in the MOP file I changed RS_MSSQLSERVER to simplyMSSQLSERVER, ran the command line utility but am still seeing the same error. Will this not work with a default instance?

This sounds like a different issue... Report Manager does not use the WMI provider to connect to teh report server. So if you're using Report Manager, then you'll need to try setting the ReportServerUrl property in the rsreportserver.config (RS 2008) or rswebapplication.config (RS2005) to point to the report server virtual directory.What else could be happening is that you may not be passing your Forms Auth cookie. Try setting the PassThroughCookies element in the configuration file for RM. What else could be happening is that your Forms Auth implementation is redirecting the user toan HTTP site due to a logon failure. This would make report manager display error messages.Hoep that helps,-LukaszThis posting is provided "AS IS" with no warranties, and confers no rights.

Nope this doesn't work for me, or your instructions aren't clear. In step 5, what should the "modified instance name"? I don't have a named instance. I also don't see the text RS_SQL2008 in my file. Also what is the unmodified instance name? I also don't understand why I am replacing something "modified" with something that's "unmodified" - surely, I replace an unmodified version with a modified one? Maybe I am not understanding your language properly. I tried replacing RS_ with [nothing] and recompiled, but it still gave the same error (invalid namespace). Here is my original MOF file - maybe you could tell me exactly for what I need to find and replace? #pragma autorecover #pragma namespace ("\\\\.\\Root") instance of __Namespace { Name = "Microsoft"; }; #pragma namespace ("\\\\.\\Root\\Microsoft") instance of __Namespace { Name = "SqlServer"; }; #pragma namespace ("\\\\.\\root\\Microsoft\\SqlServer") instance of __Namespace { Name = "ReportServer"; }; #pragma namespace ("\\\\.\\root\\Microsoft\\SqlServer\\ReportServer") instance of __Namespace { Name = "RS_MSSQLSERVER"; }; #pragma namespace ("\\\\.\\root\\Microsoft\\SqlServer\\ReportServer\\RS_MSSQLSERVER") instance of __Namespace { Name = "v10"; }; #pragma namespace ("\\\\.\\root\\Microsoft\\SqlServer\\ReportServer\\RS_MSSQLSERVER\\V10") //************************************************************* //*** Namespace: v10 *** //************************************************************* instance of __Win32Provider as $P { Name = "ReportingServicesWMI"; ClsId = "{718032C8-EDE1-4C52-9745-6D9A7B478413}"; HostingModel = "LocalSystemHostOrSelfHost"; }; instance of __InstanceProviderRegistration { Provider = $P; SupportsGet = TRUE; SupportsPut = FALSE; SupportsDelete = FALSE; SupportsEnumeration = TRUE; QuerySupportLevels = {"WQL:UnarySelect"}; }; instance of __MethodProviderRegistration { Provider = $P; }; //************************************************************************** //* Class: MSReportServer_Instance (lives in v10) //************************************************************************** [dynamic: ToInstance, provider("ReportingServicesWMI")] class MSReportServer_Instance { [read] string InstanceID; [key, read] string InstanceName; [read] uint32 EditionID; [read] string EditionName; [read] boolean IsSharePointIntegrated; [read] string Version; [implemented] void GetReportServerUrls( [out] string ApplicationName[], [out] string URLs[], [out] sint32 Length, [out] sint32 HRESULT); }; instance of __Namespace { Name = "Admin"; }; #pragma namespace ("\\\\.\\root\\Microsoft\\SqlServer\\ReportServer\\RS_MSSQLSERVER\\V10\\admin") //************************************************************* //*** Namespace: Admin *** //************************************************************* instance of __Win32Provider as $Q { Name = "ReportingServicesWMI"; ClsId = "{718032C8-EDE1-4C52-9745-6D9A7B478413}"; HostingModel = "LocalSystemHostOrSelfHost"; }; instance of __InstanceProviderRegistration { Provider = $Q; SupportsGet = TRUE; SupportsPut = TRUE; SupportsDelete = FALSE; SupportsEnumeration = TRUE; QuerySupportLevels = {"WQL:UnarySelect"}; }; instance of __MethodProviderRegistration { Provider = $Q; }; //************************************************************************** //* Class: MSReportServer_ConfigurationSetting (lives in Admin) //************************************************************************** [dynamic: ToInstance, provider("ReportingServicesWMI")] class MSReportServer_ConfigurationSetting { [read] sint32 ConnectionPoolSize; [read] string DatabaseLogonAccount; [read] sint32 DatabaseLogonTimeout; [read] sint32 DatabaseLogonType; [read] string DatabaseName; [read] sint32 DatabaseQueryTimeout; [read] string DatabaseServerName; [key, read] string InstanceName; [read] string InstallationID; [read] boolean IsInitialized; [read] boolean IsWindowsServiceEnabled; [read] boolean IsWebServiceEnabled; [read] boolean IsReportManagerEnabled; [read] string MachineAccountIdentity; [read] string PathName; [read] sint32 SecureConnectionLevel; [read] string SenderEmailAddress; [read] string ServiceName; [read] boolean SendUsingSMTPServer; [read] string SMTPServer; [read] string UnattendedExecutionAccount; [read] string WindowsServiceIdentityActual; [read] string WindowsServiceIdentityConfigured; [read] boolean IsSharePointIntegrated; [read] string Version; [read] string VirtualDirectoryReportServer; [read] string VirtualDirectoryReportManager; [implemented] void InitializeReportServer( [in] string InstallationID, [out] sint32 HRESULT, [out] string ExtendedErrors[]); [implemented] void SetUnattendedExecutionAccount( [in] string UserName, [in] string Password, [out] sint32 HRESULT); [implemented] void RemoveUnattendedExecutionAccount( [out] sint32 HRESULT); [implemented] sint32 SetDatabaseConnection( [in] string Server, [in] string DatabaseName, [in] sint32 CredentialsType, [in] string UserName, [in] string Password, [out] sint32 HRESULT); [implemented] void SetEmailConfiguration( [in] boolean SendUsingSmtpServer, [in] string SmtpServer, [in] string SenderEmailAddress, [out] sint32 HRESULT); [implemented] sint32 SetWindowsServiceIdentity( [in] boolean UseBuiltInAccount, [in] string Account, [in] string Password, [out] sint32 HRESULT); [implemented] void GenerateDatabaseCreationScript( [in] string DatabaseName, [in] sint32 Lcid, [in] boolean IsSharePointMode, [out] string Script, [out] sint32 HRESULT); [implemented] void GenerateDatabaseRightsScript( [in] string UserName, [in] string DatabaseName, [in] boolean IsRemote, [in] boolean IsWindowsUser, [out] string Script, [out] sint32 HRESULT); [implemented] void GenerateDatabaseUpgradeScript( [in] string DatabaseName, [in] string ServerVersion, [out] string Script, [out] sint32 HRESULT); [implemented] void BackupEncryptionKey( [in] string Password, [out] uint8 KeyFile[], [out] sint32 Length, [out] sint32 HRESULT, [out] string ExtendedErrors[]); [implemented] void RestoreEncryptionKey( [in] uint8 KeyFile[], [in] sint32 Length, [in] string Password, [out] sint32 HRESULT, [out] string ExtendedErrors[]); [implemented] void SetSecureConnectionLevel( [in] sint32 Level, [out] sint32 HRESULT); [implemented] void DeleteEncryptedInformation( [out] sint32 HRESULT, [out] string ExtendedErrors[]); [implemented] void DeleteEncryptionKey( [in] string InstallationID, [out] sint32 HRESULT, [out] string ExtendedErrors[]); [implemented] void ListReportServersInDatabase( [out] string MachineNames[], [out] string InstanceNames[], [out] string InstallationIDs[], [out] boolean IsInitialized[], [out] sint32 Length, [out] sint32 HRESULT, [out] string ExtendedErrors[]); [implemented] void ReencryptSecureInformation( [out] sint32 HRESULT, [out] string ExtendedErrors[]); [implemented] void SetDatabaseLogonTimeout( [in] sint32 LogonTimeout, [out] sint32 HRESULT); [implemented] void SetDatabaseQueryTimeout( [in] sint32 QueryTimeout, [out] sint32 HRESULT); [implemented] void SetServiceState( [in] boolean EnableWindowsService, [in] boolean EnableWebService, [in] boolean EnableReportManager, [out] sint32 HRESULT); [implemented] void ListInstalledSharePointVersions( [out] string VersionTokens[], [out] sint32 Length, [out] sint32 HRESULT); [implemented] void GetDatabaseVersionDisplayName( [in] string Version, [out] string DisplayName, [out] sint32 HRESULT); [implemented] void GetAdminSiteUrl( [out] string AdminSiteUrl, [out] sint32 HRESULT); [implemented] void ListReservedUrls( [out] string Application[], [out] string UrlString[], [out] string Account[], [out] string AccountSID[], [out] sint32 Length, [out] sint32 HRESULT); [implemented] void SetVirtualDirectory( [in] string Application, [in] string VirtualDirectory, [in] sint32 Lcid, [out] string Error, [out] sint32 HRESULT); [implemented] void ReserveURL( [in] string Application, [in] string UrlString, [in] sint32 Lcid, [out] string Error, [out] sint32 HRESULT); [implemented] void RemoveURL( [in] string Application, [in] string UrlString, [in] sint32 Lcid, [out] string Error, [out] sint32 HRESULT); [implemented] void ListSSLCertificates( [out] string CertificateHash[], [out] string CertName[], [out] string Hostname[], [out] sint32 Length, [out] sint32 HRESULT); [implemented] void ListIPAddresses( [out] string IPAddress[], [out] string IPVersion[], [out] boolean IsDhcpEnabled[], [out] sint32 Length, [out] sint32 HRESULT); [implemented] void ListSSLCertificateBindings( [in] sint32 Lcid, [out] string Application[], [out] string CertificateHash[], [out] string IPAddress[], [out] sint32 Port[], [out] string Errors[], [out] sint32 Length, [out] sint32 HRESULT); [implemented] void CreateSSLCertificateBinding( [in] string Application, [in] string CertificateHash, [in] string IPAddress, [in] sint32 Port, [in] sint32 Lcid, [out] string Error, [out] sint32 HRESULT); [implemented] void RemoveSSLCertificateBindings( [in] string Application, [in] string CertificateHash, [in] string IPAddress, [in] sint32 Port, [in] sint32 Lcid, [out] string Error, [out] sint32 HRESULT); };

Sorry CoLeichty - I accidentally marked yoru post as an answer...See Dave's response above. In the .MOF file Dave talks about you'll a number of lines that look like:\\\\.\\root\\Microsoft\\SqlServer\\ReportServer\\RS_MSSQLSERVERYou'll need to follow his steps and use notepad or your favorite text editor to change all instances of "RS_MSSQLSERVER" to just "MSSQLSERVER". If you chose a named instance you'll see RS_<namedinstancename>, change those to just <instancename>.If this doesn't work for you, I'd suggest calling Customer Support Services so they can help diagnose the problem in your environment.Hope that helps,-LukaszGot a bug or feature request? Tell me about it at http://connect.microsoft.com. This posting is provided "AS IS" with no warranties, and confers no rights.

Hey all. I have a somewhat similar problem. I am running Vista Business SP1. Trying to setup Reporting Services 2008. Got 2008 SQl Server Express running on my computer. It works fine. Can't configure RS though. When I enter my server name 'ESHAWKES-PC' in the 'Server Name:' textbox and hit the 'Find' button I get the error - Invalid Class. Any ideas why that is? Does it not like this servername? I haven't been able to find any info about the Invalid Class error in my research. Like I said though I don't have other problems with SQL Server. I login fine to SSMS. Can query and play around no problem.Any thoughts would be much appreciated.Have a good week btw.Ed HawkesOla Amigo

Ed,I'll try to help with this. I have not seen an "Invalid Class" error except then I have a debug version of our WMI provider on a machine that does NOT have the debug native runtime dlls (usually that means a machine that does not have a development environment). Also, an interesting note is that your machine name has a hyphen in it, I don't know if I have specifically tested this WMI provider on a machine with a hyphen (if I have is was totally by accident). I don't know that it is an issue, I just find it curious.I expect this might take several back and forths to find out the issue.So to get started, I would like to have to turn on the Reporting Services WMI logging. This is accomplished by setting a registry value. The registry key is HKLM\SOFTWARE\MICROSOFT\Microsoft SQL Server\Reporting Services. The value is a string value named "RSWMILogging" and set the Value data to the number 2. All this information assumes you are on a 32 bit operating system. If you are on a 64 bit OS, then the registry key is HKLM\SOFTWARE\wow6432Node\Microsoft\Microsoft SQL Server\Reporting Services. This is because the configuration tool is a 32 bit version and it will attach to the 32 bit version of our WMI provider.By setting this registry value, our WMI provider will start logging all queries to a file. The file will be located in the same directory as the RS WMI provider (c:\program files\Microsoft SQL Server\100\shared). Again, if this is a 64 bit OS, then it will be c:\program files (x86)\Microsoft SQL Server\100\shared.Then you should go to the Administrative Tools->Services and restart the WMI service (Windows Management Instrumentation). And try to connect to the Reporting Services instance again and let me know the contents of the WMI log file. Oh byt the way, the log file will be named ReportingServicesWMI_... .logwhere the ... will be a date and time stamp.-DaveDave This information is provided 'AS IS' with no warranties, and confers no rights.

Dave, thanks for the help. I dont see this key though. I did a search for RSWMILogging and didn't find it. I don't have this in the reg:HKLM\SOFTWARE\MICROSOFT\Microsoft SQL Server\Reporting ServicesMy HKLM\SOFTWARE\MICROSOFT dir has:HKLM\SOFTWARE\MICROSOFT\MSRS10.SQLEXPRESS2008 HKLM\SOFTWARE\MICROSOFT\MSSQLServer HKLM\SOFTWARE\MICROSOFT\SQLEXPRESS2008 I did see this though in the VisualStudio dir:System.Management.Instrumentation\System.Management.Instrumentation.WmiProviderInstallationExceptionMaybe the WMI install I have is what's off? I'm not sure what this guy does to be honest.Anyway, thanks again for the help. Let me know what you think if you have any clues.Gracias.Ed HawkesOla Amigo

I'm sorry I was not more explicit. You will NOT see the key, you will need to add it. By default, our WMI logging is turned off and the key does not exist.From you registry, it looks like you might have more than one instance of SQL Server on your machine, is that correct? What is the version of the MSSQLSERVER instance?Also you can look at this page:http://msdn.microsoft.com/en-us/library/aa394603(VS.85).aspxOn the page, there is reference to a WMI Diagnosis Utility. You can down load it and follow the instructions to see if your WMI install is faulty. as I remember, it is pretty verbose, but if there is a problem the instructions should help you find and isolate it. I would not necessarily suspect the WMI installation, unless you are having other troubles with your machine.-DaveDave This information is provided 'AS IS' with no warranties, and confers no rights.

Hey Dave,Here is the version of SQL Server I have according to SSMS - Microsoft SQL Server Management Studio10.0.1600.22 ((SQL_PreRelease).080709-1414 )Microsoft Data Access Components (MDAC)6.0.6001.18000 (longhorn_rtm.080118-1840)Microsoft MSXML3.0 5.0 6.0 Microsoft Internet Explorer8.0.6001.18813Microsoft .NET Framework2.0.50727.3074Operating System6.0.6001It lives in:C:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS2008\MSSQLAFAIK it's SQL SERVER 2008 Express edition. I'm still trying to figure out where to put this key. I am not sure where WMI lives in my computer.SSRS is installed at - C:\Program Files\Microsoft SQL Server\MSRS10.SQLEXPRESS2008I put a registry key - RSWMILogging, in the corresponding HKLM spot in the reg, with the value 2. Can't see anylog files being created.Thanks Ed.Ola Amigo

Ok, you added the "Reporting Services" key (since it wasn't there) and within the key you added the RSWMILogging string value.Did you re-start the WMI service? If so, and if launching the RS Configuration Tool did NOT result in any log files, WMI is not finding the RS WMI provider.Next I will try to walk you through some useful WMI tricks. There is a tool on your machine called WBEMTEST.EXE. You can go Start->run->WBEMTEST.EXE to launch it.This tool is a GUI tool to interact with WMI. The first thing you notice is all the buttons you have available, we will use only a few. The first button is the "Connect..." button. Press it and enter root\microsoft\sqlserver\reportserver . The press the "Connect" button.Now you should see the original dialog with all the buttons enabled. Press the "Query..." Button. Enter the following query - "select * from __namespace" (without the quotes). Notice that there are two underscores (_) before namespace. Press the "Apply" button.This will give you a list of all of the reporting services instance WMI thinks you have. Will next append this string to the connection string and try the query again. We will keep doing this for couple more iterations until we isolate the problem, so bare with me on this.Let me know the results of the first query and I'll walk you though the remainder of these queries.-DaveDave This information is provided 'AS IS' with no warranties, and confers no rights.

Ok, you added the "Reporting Services" key (since it wasn't there) and within the key you added the RSWMILogging string value.Did you re-start the WMI service? YES If so, and if launching the RS Configuration Tool did NOT result in any log files, WMI is not finding the RS WMI provider...This tool is a GUI tool to interact with WMI. The first thing you notice is all the buttons you have available, we will use only a few. The first button is the "Connect..." button. Press it and enter root\microsoft\sqlserver\reportserver . The press the "Connect" button.I press connect and get: Number 0x8004100e, Facility WMI, Description: Invalid NamespaceFWIW, when I run the query against the default root, 'root\cimv2'I get 4 rows back:__NAMESPACE.Name="Security"__NAMESPACE.Name="ms_409"__NAMESPACE.Name="TerminalServices"__NAMESPACE.Name="Applications"Ola Amigo

BTW Dave, thanks again for the help. I'm setting this up asa home dvlp thing so it's not critical. I am interested in what's going on. Very much a learning thing for me.Ola Amigo

Ed,It looks to me like our WMI provider is not registered. This will be a two step process. The first step it to find and re-register the MOF file. This file has the definition of our WMI interfaces. It will be located in one of the directories that we installed with Reporting Services. It is best to use a command window for these two steps. If you are running on Vista, or Windows 7, you will need to laund the command window as the administrator (Right click on the command promp window and choose "Run as Administrator". On Xp you don't need to do this.Navigate to the %PROGRAMFILES%\Microsoft SQl Server\MSRS10......\Reporting Services\ReportServer\bin directory. Since I don't know the name of your instances I don't know how to complete the MSRS10..... reference (based on your registry information it could be MSRS10.SQLEXPRESS2008).In this directory you should find a file named ReportingSerivces.MOF. To register it, type MOFCOMP.EXE REPORTINSERVICES.MOFNow we need to register the actual code that does the work. Naviagate up 4 directories (cd ..\..\..\.. )which should put you at the %PROGRAMFILES%\Microsoft SQL Server directory. Now cd 100\shared. To register the DLL type "REGSVR32 REPORTINGSERVICESWMI.DLL" (Please verify the DLL name by typing DIR REP* and use the only file with a file extension of DLL).Then you can try the Reporting Services Configuration tool again.Dave This information is provided 'AS IS' with no warranties, and confers no rights.

It would be interesting if you ran Repair in setup and if it still doesn't work thereafter send the setup log files to us using http://connect.microsoft.com Hope that helps, -LukaszGot a bug or feature request? Tell me about it at http://connect.microsoft.com. This posting is provided "AS IS" with no warranties, and confers no rights.

Dave. Thanks for the help. No luck alas. Same 'Invalid Class' error.Ola Amigo

Lukasz. Thanks for the help. No luck. I signed on with connect. Gotta figure out how to post the log files and/or create a bug for this.Heres the summary log I get after running repair, fwiw:Overall summary: Final result: Passed Exit code (Decimal): 0 Exit message: Passed Start time: 2009-09-29 20:03:47 End time: 2009-09-29 20:15:04 Requested action: Repair Machine Properties: Machine name: ESHAWKES-PC Machine processor count: 4 OS version: Windows Vista OS service pack: Service Pack 1 OS region: United States OS language: English (United States) OS architecture: x86 Process architecture: 32 Bit OS clustered: No Product features discovered: Product Instance Instance ID Feature Language Edition Version Clustered Sql Server 2008 SQLEXPRESS2008 MSSQL10.SQLEXPRESS2008 Database Engine Services 1033 Express Edition 10.0.1600.22 No Sql Server 2008 SQLEXPRESS2008 MSSQL10.SQLEXPRESS2008 SQL Server Replication 1033 Express Edition 10.0.1600.22 No Sql Server 2008 SQLEXPRESS2008 MSSQL10.SQLEXPRESS2008 Full-Text Search 1033 Express Edition 10.0.1600.22 No Sql Server 2008 SQLEXPRESS2008 MSRS10.SQLEXPRESS2008 Reporting Services 1033 Express Edition 10.0.1600.22 No Sql Server 2008 Management Tools - Basic 1033 Express Edition 10.0.1600.22 No Sql Server 2008 IS_CTP5 1033 Developer Edition 10.0.1075.23 No Package properties: Description: SQL Server Database Services 2008 SQLProductFamilyCode: {628F8F38-600E-493D-9946-F4178F20A8A9} ProductName: SQL2008 Type: RTM Version: 10 SPLevel: 0 Installation location: c:\740fc58b485e7f6b9157596273\x86\setup\ Installation edition: EXPRESS_ADVANCED User Input Settings: ACTION: Repair AGTDOMAINGROUP: <empty> AGTSVCACCOUNT: <empty> AGTSVCPASSWORD: ***** AGTSVCSTARTUPTYPE: Manual ASCONFIGDIR: Config ASDOMAINGROUP: <empty> ASSVCACCOUNT: <empty> ASSVCPASSWORD: ***** CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20090929_200243\ConfigurationFile.ini FAILOVERCLUSTERGROUP: <empty> FAILOVERCLUSTERNETWORKNAME: <empty> FTSVCACCOUNT: NT AUTHORITY\LOCAL SERVICE FTSVCPASSWORD: ***** HELP: False INDICATEPROGRESS: False INSTANCENAME: SQLEXPRESS2008 ISSVCACCOUNT: NT AUTHORITY\NetworkService ISSVCPASSWORD: ***** ISSVCSTARTUPTYPE: Automatic QUIET: False QUIETSIMPLE: False SQLDOMAINGROUP: <empty> SQLSVCACCOUNT: <empty> SQLSVCPASSWORD: ***** X86: False Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20090929_200243\ConfigurationFile.ini Detailed results: Feature: Database Engine Services Status: Passed MSI status: Passed Configuration status: Passed Feature: SQL Client Connectivity Status: Passed MSI status: Passed Configuration status: Passed Feature: SQL Client Connectivity SDK Status: Passed MSI status: Passed Configuration status: Passed Feature: SQL Writer Status: Passed MSI status: Passed Configuration status: Passed Feature: SQL Browser Status: Passed MSI status: Passed Configuration status: Passed Feature: SQL Server Replication Status: Passed MSI status: Passed Configuration status: Passed Feature: Full-Text Search Status: Passed MSI status: Passed Configuration status: Passed Feature: Reporting Services Status: Passed MSI status: Passed Configuration status: Passed Feature: SQL Compact Edition Tools Status: Passed MSI status: Passed Configuration status: Passed Feature: SQL Compact Edition Runtime Status: Passed MSI status: Passed Configuration status: Passed Feature: Management Tools - Basic Status: Passed MSI status: Passed Configuration status: Passed Feature: Business Intelligence Development Studio Status: Passed MSI status: Passed Configuration status: Passed Feature: Microsoft Sync Framework Status: Passed MSI status: Passed Configuration status: Passed Rules with failures: Global rules: There are no scenario-specific rules. Rules report file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20090929_200243\SystemConfigurationCheck_Report.htm The following warnings were encountered while configuring settings on your SQL Server. These resources / settings were missing or invalid so default values were used in recreating the missing resources. Please review to make sure they dont require further customization for your applications: Service SID support has been enabled on the service.Service SID support has been enabled on the service.Ola Amigo

Thank you Dave, Worked like a charmDan Eaton

I am getting this same Invalid name space error while connecting to SSRS 2005 from SSRS 2008 through reporting services configuration manager. Both the SQL 2005 and SQL 2008 are in different machines. ANy help on this would be really appreciated!Veeramani.S

Steps to modify the MOF file to fix this issue: 1. Locate the existing MOF file (example: %ProgamFiles%\Microsoft SQL Server\MSRS10.SQL2008\Reporting Services\ReportServer\bin\reportingservices.mof would be the default location for a Reporting Services instance named SQL2008). 2. Copy this reportingservices.mof to reportingservicesalt.mof (or some other unique name). 3. Notepad reportingservicealt.mof 4. Choose edit->replace… 5. In the dialog, in the Find What: text box enter the modified instance name (for an RS instance named SQL2008, the modified instance name is RS_SQL2008), in the Replace with: text box enter the instance name unmodified (so for an RS instance named SQL2008, just enter SQL2008). 6. Press the Replace All button. 7. Save and close notepad. 8. From a command window at the same location as the results of step 1, type MOFCOMP REPORTINSERVICESALT.MOF (or whatever the name from step 2 was). Now the configuration tool should work with the following exception, if the RS instance name contains an underscore (_), a dollar sign ($) or a hash (#), then step 8 will fail and the user will need to re-install the Reporting Services instance with a name that does not include any of these three characters. Perfect Solution It works for me 100% , many many many thansssssssssssssssssssssss There is no impossible

So I'm in a very similar situation but with the following nuances: SQL 2005 was installed (since removed) Opening Reporting Services Configuration Manager (RSCM) and using the server name alone ('JM-SERVER') and pressing 'Find' - I get the simplistic 'Invalid Class' error. Changing this to 'JM-SERVER\SpecificInstanceName' I get a "Report Server WMI Provider error: 'Invalid Namespace' Details: 'Invalid Namespace' " error? I've tried every suggestion here relating to .MOF files, re-registering the reportingservicesWMI.dll and re-installing the report server... still no luck. All the WBEMTEST process checks out ok and I can connect via the URL... RSCM just won't work. Has anyone else managed to have success in resolving this problem?

Hi Dave, Using RS2008... shortcut path is "C:\Program Files\Microsoft SQL Server\100\Tools\Binn\RSConfigTool.exe"... I'm currently in the process of re-installing and removing SQL 2005 as I recall some difficulty in the uninstall some time back. I should also add that I've re-installed SQL 2008 and also tried repairing the installation... no luck either way. Here's some further information that I've recently discovered... Trying to connect to the report server remotely (still using RSCM 2008 - just installed on a different server) I get the error "A connection to the computer cannot be established Details: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))" And going further down the rabbit hole... based on the error above I stumbled across this http://social.msdn.microsoft.com/Forums/en-ZA/vsreportcontrols/thread/26accc30-9cfb-4d86-9c27-780f51929ecb Following MikeAtOpco's second suggestion I navigate to DCOM Config (under Component Services) and am presented with ~4 of the following warnings/options: "DCOM Configuration Warning! The CLSID {...}, item C:\WINDOWS\system32\wbem\wmiprvse.exe and the title Microsoft WMI Provider Subsystem Secured Host has the named value AppID, but is not recorded under \\HKEY_CLASSES_ROOT\AppID. Do you wish to record it?" I clicked Yes to each one and made the changes suggested - will notify if there's any change...

This was helpful in combination with the accepted solution. We had to change the "[specified instance]" in our file to our name (in our case WWWSQL08). Worked like a charm.

Thanks Neeraja, That worked for me with SQL2005 server. scorpITs | http://scorpITs.blogspot.com